I'll wait on it and see first what winbar can best be used for . Also what ideas community can come up with for winbar . vim has had winbar for long time and tbh I've only noticed it to be used in vimspector.

For now I don't think using winbar just as a statusline is a good idea . I'll prefer to have winbar to be buffer specific unlike global . A winbar specific plugin can probably pull it of better than if just treat is as part of statusline in lualine.

So I'm putting it on hold . Not entirely rejecting it nor accepting the idea.

@shadmansaleh
I agree with you.
I implement this for me to try what I feel when use winbar as status bar. But I found #688, so I decided to create a PR for who interested in this.

btw I think winbar is a nice place to have information like nvim-gps, lsp-signature's statusline and lsp status.

@diegodox exactly what I want. There is a lot of buffer specific info in my global statusline at the moment.
Just putting the file name > class > method > matchparen of the current cursor position is probably all I want for the winbar.

PS: I found winbar is only reasonable place to show filename of each buffer (especially inactive buffer) with global status line.

The most useful points of winbar are:

1. Full path of the filename (%F)
2. LSP symbol path (aerial.nvim has API to output this)
3. Window number (vim.api.nvim_win_get_number())

Setting them is very easy and no need further supports. I believe a fancy statusline is necessary but a plus fancy winbar at the top will be distracting. Also, a verbose and complicated winbar will get truncated and making it meaningless at all.

Sorry for being totally off topic here guys...

But @rockyzhang24, do you mind sharing your font and color scheme from that screenshot?

@bellini666 No problem.

do you mind sharing your font and color scheme from that screenshot?

Font: JetBrainsMono
Color scheme: nightfox.nvim and I configured some colors that are not easily distinguished (See this please if you need: https://github.com/rockyzhang24/dotfiles/blob/master/.config/nvim/lua/plugin/nightfox.lua)

Furthermore, with the creation of nvim-navic, I think the community has certainly made up it's mind about the utility of the winbar.

imho statusline and winbar aim different purposes, statusline for more global things, which are shared across splits, and winbar are about some specific splint only

@alex-popov-tech I think the ideal approach would be to be flexible enough for users to display whatever information they want on each. Like we do now with lualine sections, but having an extra set of section keys in the configuration for winbar sections. It already supports statusline and tabline this way, why not winbar as well?

In a perfect world users would be able to add lualine components and extensions currently used for statusline to the winbar, and vice-versa.

As you point out, a popular configuration could be winbar for buffer specific info and statusline for global/project level info. Another one could be, for example, statusline for the focused buffer (with a more detailed view) and winbar for inactive buffers. Someone might not care about diagnostic info on inactive buffers, while someone else might want to see which lsp clients are attached to each buffer instead of globally (for whatever reason).

@diegodox I'd like to add that because you set the global winbar (vim.go instead of vim.wo) to winbar() it becomes difficult to disable lualine winbar on certain files in a different window. For example, disabling the winbar on NvimTree sidebar becomes basically impossible because setting vim.wo.winbar subsequently has no effect.

Sorry if this is bothersome but I know a lot of people will be bothered by there being an empty winbar essentially wasting space in a buffer.

@diegodox I've pulled the changed from this branch to #736 .

Would appreciate if you guys interested in the feature can test it.

@barrett-ruth Thank you for pointing out vim.go.winbar will not respect vim.wo.winbar. I'm planning to fix that (use vim.wo.winbar instead of vim.go.winbar). And sorry for late reply.
But sorry again, I have no time to impl that right now. Anyone who want to impl that feature are welcome. :)
I might find time in 1 month.

Need advice on implementation approach, is autocmd right choice to set winbar window option? or more simpler way exists?

@shadmansaleh I will look and test that branch, thank you.

Thank you for pointing out vim.go.winbar will not respect vim.wo.winbar. I'm planning to fix that (use vim.wo.winbar instead of vim.go.winbar). And sorry for late reply.
But sorry again, I have no time to impl that right now. Anyone who want to impl that feature are welcome. :)

addressing that issue is the purpose of #736 . So lualine can keep running even when options are unset.

Merged with #736 in 53aa3d8